Page History: Logon
Compare Page Revisions
Page Revision: 2012/09/06 15:25
Session InitiationAfter a sucessful TCP (socket) connection, the T4 FIX API basic requirement is to have both the Initiator and Acceptor start with sequence number 1. The client will initiate the FIX Session by sending a Logon Message to the T4 FIX API server. Sucessful authentication will be responded with a Logon message echo. The Password field (Tag 96) of the API server logon message will be identified with an asterisk.
Drop of a physical connection will result in the end of a FIX Session. Upon reconnection, the client will attempt to start a new FIX Session with sequence number 1. Likewise, the T4 API server will respond with messages starting with sequence number 1.
Authentication RequirementsFollowing a sucessful physical connection to the T4 FIX API server, authenticated access is achieved with the following parameters of the client's Logon message:
Tag Name | Tag Number | Description |
---|
TargetCompId | 56 | FIX API System |
SenderCompId | 49 | Firm Name |
SecureData | 91 | Application ID (FIX API ID) |
SecureDataLen | 90 | Length of Application ID string |
SenderSubId | 50 | Firm User Name (Trader name, desk, etc.) |
RawData | 96 | Firm User Password |
RawDataLen | 95 | Length of Firm User Password string |
Failure to provide the correct parameters in the Logon message will result in an logon failure. Appropriately, a
Logout message will be sent to the client. The Logout message will contain a short description of the failure to help determine the cause of failed authentication. Thereafter, a physical disconnection will occur. As the FIX Session failed, the T4 FIX API will expect a new attempt for a new FIX session. The next Logon message (from the client) must start with sequence number 1.
Message DictionaryTag | Field Name | Req'd | Comments |
---|
| Standard Header | Y | MsgType = A |
91 | SecureData | Y | FIX API ID. Please contact your FIX API Administrator for your authorized id. |
90 | SecureDataLen | Y | Length of SecureData string |
49 | SenderCompID | Y | Assigned value used to identify firm sending message |
56 | TargetCompID | Y | Assigned value used to identify receiving firm |
50 | SenderSubID | Y | Assigned value used to identify specific message originator (trader, desk, etc.) |
| Body | Y | |
98 | EncryptMethod | Y | (Always unencrypted). Value = None |
108 | HeartBtInt | Y | Heartbeat interval. Set to 30 seconds. |
95 | RawDataLength | Y | Length of user Password string |
96 | RawData | Y | Password for user authentication |
141 | ResetSeqNumFlag | N | Not used. Indicates both sides of a FIX session should reset sequence numbers |
383 | MaxMessageSize | N | Not used. Can be used to specify the maximum number of bytes supported for messages received |
384 | NoMsgType Group | N | Not used. Specifies the number of repeating MsgTypes specified |
| Standard Trailer | Y |
Sample Message
34=1|49=test|56=T4Test|50=TraderName|52=20120904-17:37:16.848|91=64768859-3DCF-4214-A4E8-DA66881AFC63|90=36|95=10|96=_password_|98=None|108=30|
[FIXLOGIN]
[MsgSeqNum] 34 = 1
[SenderCompID] 49 = test
[TargetCompID] 56 = T4Test
[SenderSubID] 50 = TraderName
[SendingTime] 52 = 20120904-17:33:50.398
[SecureData] 91 = 64768859-3DCF-4214-A4E8-DA66881AFC63
[SecureDataLen] 90 = 36
[RawDataLength] 95 = 10
[RawData] 96 = _password_
[EncryptMethod] 98 = None
[HeartBtInt] 108 = 30
FIX API Home Page.